home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19971216-19980424
/
000400_news@newsmaster….columbia.edu _Wed Apr 8 09:45:06 1998.msg
< prev
next >
Wrap
Internet Message Format
|
1998-04-22
|
4KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id JAA23616
for <kermit.misc@watsun.cc.columbia.edu>; Wed, 8 Apr 1998 09:45:06 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id JAA28359
for kermit.misc@watsun; Wed, 8 Apr 1998 09:45:05 -0400 (EDT)
Path: news.columbia.edu!sol.ctr.columbia.edu!news.uoregon.edu!logbridge.uoregon.edu!howland.erols.net!news-peer.sprintlink.net!news-backup-east.sprintlink.net!news-in-east.sprintlink.net!news.sprintlink.net!Sprint!209.90.0.8!alpha.sky.net!newshub.cts.com!newshub.nosc.mil!dog.ee.lbl.gov!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Msdos Kermit & Windows 95 DOS prompt.
Message-ID: <SGYKcvvLy6si@cc.usu.edu>
Date: 7 Apr 98 10:17:01 MDT
References: <3529944E.1ACDB07A@netlink.com.au>
Organization: Utah State University
Lines: 79
Xref: news.columbia.edu comp.protocols.kermit.misc:8603
In article <3529944E.1ACDB07A@netlink.com.au>, Ross Irvine <rirvine@netlink.com.au> writes:
> Hello All,
> I have a situation where at some of my remote sites I use
> ms dos kermit 3.15 to transfere some files overnight.
>
> The PC's reboot into windows 95 command prompt only (eg no windows GUI)
> to run Kermit. I have to use kermit for dos as kermit95 (which I also
> have) will not run in the command prompt mode as it's not a 32bit
> environment.
>
> My problem is setting the com port in DOS. Here's an example of what
> happens :
>
> ** START EXAMPLE
> MS-DOS Kermit: 3.15 15 Sept 1997 patch level 1
> Executing F:\MIS\ISDN\REGISTRY\KERMIT\MSKERMIT.PCH...
> Installing patches...
>
> MS-DOS Kermit 3.15 Initialization File...
> Dialing directory "F:\MIS\ISDN\REGISTRY\KERMIT\DIALUPS.TXT" not found.
> ?Warning: unknown hardware for port. Using the Bios as BIOS1
> Unimplemented speed
> ?Cannot use RTS/CTS on non-UART ports
> Smile!
> [F:\MIS\ISDN\REGISTRY\KERMIT] MS-Kermit>quit
> Bye!
> F:\MIS\ISDN\REGISTRY\KERMIT>kermit
> IBM-PC MS-DOS Kermit: 3.15 15 Sept 1997
> Copyright (C) Trustees of Columbia University 1982, 1997.
>
> Type ? or HELP for help
> MS-DOS Kermit: 3.15 15 Sept 1997 patch level 1
> Executing F:\MIS\ISDN\REGISTRY\KERMIT\MSKERMIT.PCH...
> Installing patches...
>
> MS-DOS Kermit 3.15 Initialization File...
> Dialing directory "F:\MIS\ISDN\REGISTRY\KERMIT\DIALUPS.TXT" not found.
> Smile!
> [F:\MIS\ISDN\REGISTRY\KERMIT] MS-Kermit>
>
> ** END EXAMPLE
>
> The line it's dying on in the mscustom.ini files is:
> set port 1
>
> As you can see, the first time I ran kermit it doesn't find the com port
> and sets the port to bios 1. I then exit kermit and reload it straight
> away (without rebooting or doing anything) and kermit finds the com port
> and works happily.
>
> My question is why? This is on an old Compaq Prolinea 5100 32Meg ram,
> nothing special, normal com port settings (irq,base addres etc). It also
> seems to happen on all the PC's I have access to.
>
> Regardless of if I run it from the windows 95 command mode or in a dos
> windows inside windows 95 gui it does the same thing. Kermit 316 Alpha 5
> also does this.
>
> It just seems like sometimes it works, sometimes it doesn't.
>
> I've tried, trying to capture the warning message on the set port 1
> statement in the mscustom.ini, so I can just loop the set port 1
> staement until it works. The problem with this is that the warning
> message is all that is returned from the set port command. It does not
> return FAILURE, so I can't "test" to see if it worked or not.
>
> Should I be using "set port com1" instead of "set port 1" is there any
> difference?
>
> If anyone has any ideas I would be greatfull.
>
> regards.
--------
MS-DOS Kermit is telling the truth. Your serial port is not responding
as a real serial port when MSK tests it. This could be from IRQ conflicts,
or devices overlapping the Port address range of the serial port, or the
hardware comes up uninitialized and requires coaxing to speak clearly.
SET PORT 1 is identical to SET PORT COM1.
Joe D.